…or agentic chat (#7857)

## Problem
In order to set appropriate Origin Info on LSP side for SMAI CodeEditor,
[link](https://github.com/aws/language-servers/blob/68adf18d7ec46a7ecf9c66fd9d52b1b8f7bc236e/server/aws-lsp-codewhisperer/src/shared/utils.ts#L377),
clientInfo needs to be distinct
- related [PR to support
SMUS](#7817)

## Solution
- To check if the environment is SageMaker and a Unified Studio instance
and set corresponding clientInfo Name which is ```AmazonQ-For-SMUS-CE```

## Testing
- Built artefact locally using ```npm run compile && npm run package```
and tested on a SMAI CE space
- Ran ```npm run test -w packages/toolkit``` which succeeded
- LSP logs show the respective client Info details
```

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time.
- Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

Co-authored-by: Laxman Reddy <[email protected]>

…7839)

## Problem
Inline completion suggestions were being shown even when edit
suggestions were active, creating a confusing user experience where both
types of suggestions could appear simultaneously.

## Solution
1. Added conflict prevention logic in provideInlineCompletionItems() to
check for active edit suggestions using the existing
aws.amazonq.editSuggestionActive context flag
1. Created isEditSuggestionActive() method to encapsulate context
checking
1. Implemented DISCARD telemetry for completion suggestions that can't
be shown due to active edits
1. Added unit tests covering the new functionality, including edge cases
for mixed suggestion types and items without IDs
1. Updated displayImage.ts to properly set/unset the context flag when
edit suggestions are displayed/cleared
1. The solution ensures only one type of suggestion is active at a time
while maintaining telemetry compliance and following existing codebase
patterns.

---
Treat all work as PUBLIC. Private feature/x branches will not be
squash-merged at release time.
Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.